System and apparatus for providing policy control and charging to support communications

ABSTRACT

A system that incorporates teachings of the present disclosure may include, for example, utilizing a first diameter agent function to route messages between network elements that provide policy control and charging for a communication session, utilizing the first agent function to maintain transaction and session state during the communication session, and utilizing the first agent function to selectively adjust routing and non-routing information for the messages. Other embodiments are disclosed.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to communications and moreparticularly to providing policy control and charging for supportingcommunications.

BACKGROUND

As communications technology improves and demand for communicationservices grows, providers often seek to adjust those systems toincorporate the improved technology and expand those systems toaccommodate the growing demand. Systems that are slow to adjust orexpand can be undesirable and are often rendered obsolete. Systems thatexpand by providing unnecessary redundancy are inefficient and costly.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an illustrative embodiment of zones of a communicationsystem;

FIGS. 2-4 depict examples of interaction of a protocol stack, networkelements, and message structure for the zones of FIG. 1;

FIG. 5 depicts an exemplary configuration of network elements within thezones of FIG. 1;

FIG. 6 depicts tables for interfacing between network elements in anexemplary configuration of the communication system of FIG. 5;

FIGS. 7-8 depict interaction between network elements of thecommunication system of FIG. 5;

FIGS. 9-11 depict an illustrative embodiment for transitioning between ade facto baseline configuration to the target architecture of thecommunication system of FIG. 1;

FIG. 12 depicts tables that summarize the agents and interfaces of thebaseline architecture of FIG. 11;

FIGS. 13-16 depict an illustrative embodiment for transitioning betweensystem configurations to obtain the communication system of FIG. 5through use of a multi-stage process;

FIG. 17 depicts an illustrative embodiment of a method for providing thenetwork of FIG. 5;

FIG. 18 depicts an illustrative embodiment of a method for providingsubscriber management for the network of FIG. 5;

FIG. 19 depicts an illustrative embodiment of a method for providingpolicy control and charging for the network of FIG. 5; and

FIG. 20 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods discussedherein.

DETAILED DESCRIPTION

The present disclosure describes, among other things, illustrativeembodiments to provide a system in which the architecture can beindependent of the services being provided. Routing zones that includeone or more agents can be established where the agents can facilitaterouting between network elements of the routing zone during acommunication session. In one embodiment, the agent performing routingin the zone that processes subscriber management can be a relay agentthat selectively adjusts routing information but does not examine and/ordoes not adjust non-routing Attribute Value Pairs (AVP) in a Diameterprotocol message. The agent in the zone that performs policy control andcharging can be a proxy agent (with or without a translation agent),which selectively adjusts routing information and messages includingnon-routing AVPs.

The present application is related to U.S. application Ser. No.13/471,833 filed contemporaneously herewith which is entitled “Systemand Apparatus For Providing Communications”, the disclosure of which isincorporated herein by reference in its entirety. The presentapplication is related to U.S. application Ser. No. 13/471,855 filedcontemporaneously herewith which is entitled “System and Apparatus ForProviding Subscriber Management To Support Communications”, thedisclosure of which is incorporated herein by reference in its entirety.

One embodiment of the present disclosure describes an apparatus having amemory storing computer instructions, and a processor coupled with thememory, wherein the processor, responsive to executing the computerinstructions, performs operations including receiving messages utilizinga Diameter protocol from first network elements that provide policycontrol and charging for a communication session. The operations canalso include maintaining transaction and session state during thecommunication session where the processor selectively adjusts routingattribute value pairs and non-routing attribute value pairs for themessages. The operations can include routing the messages utilizing theDiameter protocol to second network elements that provide the policycontrol and charging. The operations can also include providing at leastone of the messages to a Diameter edge agent server that maintainstransaction and session state during the communication session forrouting the at least one message to an external network.

One embodiment of the present disclosure describes a method includingutilizing a first server to route messages between network elements thatprovide policy control and charging for a communication session,utilizing the first server to maintain transaction and session stateduring the communication session, and utilizing the first server toselectively adjust routing and non-routing information for the messages.

One embodiment of the present disclosure describes a non-transitorycomputer-readable storage medium comprising computer instruction which,responsive to being executed by a processor, cause the processor toperform operations including routing messages between network elementsthat provide policy control and charging for a communication session,maintaining transaction and session state during the communicationsession, and selectively adjusting routing and non-routing informationfor the messages.

For illustration purposes only, various functions (e.g., P-CSCF) and/orDiameter agents, such as Diameter agent functions (e.g., relay, proxyand/or translation agents), may be used herein without the word“device,” “server,” or “agent function.” It is, however, understood thatany form of an agent or function, including Diameter agents and CSCF's,operate in one or more of devices, systems, components, or other formsof centralized or distributed hardware and software. It is further notedthat these terms and other terms such as DIAMETER commands are terms caninclude features, methodologies, and/or fields that may be described inwhole or in part by standards bodies such as 3^(rd) GenerationPartnership Project (3GPP). It is further noted that some or allembodiments of the subject disclosure may in whole or in part modify,supplement, or otherwise supersede final or proposed standards publishedand promulgated by 3GPP, including generating proprietary devices and/orprocesses that include at least a portion of the standards butsupplement the standards. It should be further noted that a device orfunction that utilizes or otherwise operates according to a protocol(e.g., Diameter protocol or Radius protocol) can utilize all or alimited portion of the features of the protocol with or withoutsupplementation of other features or adjustment of existing protocolfeatures.

FIG. 1 depicts an illustrative embodiment of a communication network100, which can facilitate establishing communications via one or moretechnologies such as via an Evolved Packet System (EPS) and/or anInternet Protocol Multimedia Subsystem (IMS). Network 100 can utilizeone or more packet-based signaling protocols, such as Diameter and/orSession Initiation Protocol (SIP). In one embodiment, network 100 canoperate without utilizing signaling that is based on Signaling System #7(SS7) protocol.

In one embodiment, network 100 can employ Diameter protocol in the EPSand/or the IMS for a variety of purposes including registration,authentication, location management, the exchange of user data, policycontrol, and/or charging (e.g., online and/or offline). As an example,Diameter agents as defined in RFC 3588, the disclosure of which ishereby incorporated by reference, can be employed by the network 100 toimprove scalability by centralizing the routing of Diameter messages.

Network 100 can be divided into at least three routing zones for: theHome Subscriber Server (HSS) function (HSS relay zone 110), the policyand charging control (PCC) function (PCC zone 120), and routing messagesto and from external networks (Diameter edge zone 130). In thisembodiment, each routing zone 110, 120, 130 can make use of aspecialized Diameter agent function to route messages via Diameterinterfaces. In one embodiment, these interfaces can be standardscompliant. In another embodiment, extensions to standard interfaces mayalso be implemented in addition to, or in place of, one or more of thestandards compliant interfaces. In one embodiment, each of zones 110,120, 130 can operate independently of each other where the networkelement messages associated with the subscriber management and thepolicy control and charging do not cross zone boundaries.

Network 100 can utilize the Diameter protocol which is a peer-to-peer,extensible protocol that is intended to provide an AAA framework forapplications, such as network access or IP mobility. As shown in FIG. 2,the Diameter specification is comprised of three layers: the transportlayer, the Diameter base protocol, and the Diameter application. In oneembodiment, the Diameter protocol utilized by network 100 can make useof the AAA transport profile specified in RFC 3539, the disclosure ofwhich is hereby incorporated by reference. In one or more embodiments,the Diameter protocol being used by network 100 can be used inconjunction with one or both of Transmission Control Protocol (TCP) andStream Control Transmission Protocol (SCTP) for transport.

In one embodiment, Diameter messages in network 100 can be transportedin a synchronous manner involving request and answer messages as shownbeing transmitted between client 310 and server 320 of FIG. 3. Theclient 310 and server 320 can represent or otherwise be resident onvarious network elements found in zones 110, 120, 130 of network 100, aswill be discussed later. The Diameter client 310 can initiate a requestto a Diameter server 320 which provides an answer. The network elementor node can be a client 310 for some messages and can be a server 320for other messages. In one or more embodiments, the network element orDiameter node, can act as both the client and the server.

Each Request/Answer pair transmitted in network 100 can be a message 400(shown in FIG. 4) assigned a command code. Some command codes can bespecified in the base protocol while others can be specified by theDiameter applications. In one embodiment, data can be exchanged by useof AVPs which can be specified in the base protocol and/or in theapplications (e.g., Diameter applications). As an example, RFC 5516provides a list of command codes that are specific to the EPS while RFC3589 provides a list that is specific to the IMS. Other command codesand AVPs can also be utilized, such as those described in 3GPP TS29.230. Network 100 can also allow for the creation of new command codesand/or AVPs.

In addition to clients 310 and servers 320, network 100 can also utilizeagents as Diameter nodes. Diameter agents can be used to improvescalability and reliability by centralizing the routing of Diametermessages, while also enabling translation of messages from one AAAformat to another. The types of Diameter agents that can be used bynetwork 100 include relay agents, redirect agents, proxy agents and/ortranslation agents. Network 100 can use relay agents to route messagesbetween clients 310 and servers 320 based on information containedwithin the message 400. The relay agents can remain in the signalingpath for the duration of the Diameter session and therefore can maintaintransaction state. Relay agents can modify and/or remove routinginformation, but relay agents do not modify any other portion of themessage. Network 100 can use proxy agents which are similar to relayagents except that proxy agents can modify the entire Diameter messageor any portion thereof. As a result, proxy agents can maintain bothtransaction and session state. Network 100 can use a redirect agent thatprovides the client with information necessary to route the message tothe server. Redirect agents are not involved with the transport of theanswer message back to the client 310, nor do they modify Diametermessages. As a result, redirect agents maintain neither transaction, norsession, state. Network 100 can use translation agents to translatebetween different protocols. An example of this is a translation agentthat translates between RADIUS and Diameter protocols. Translationagents of network 100 can maintain both transaction and session state.

Referring to FIG. 5, network 500 is illustrated that depicts anexemplary configuration of network elements for the HSS relay zone 110,the PCC zone 120, and the Diameter edge zone 130. The configuration ofnetwork 500 provides network integration by reducing networkimplementations that are silo configurations. Network 500 defineslogical Diameter routing zones based on specific use cases for Diameterin the EPS and IMS. Network 500 utilizes Diameter agents to supportscalability, but minimizes their redundancy. For instance, a singleDiameter agent can be utilized in each of the HSS relay zone 110, thePCC zone 120, and the Diameter edge zone 130, although other embodimentscan use multiple agents. Network 500 can utilize various interfaces,including 3GPP interfaces.

Each of zones 110, 120, 130 can make use of a unique Diameter agentfunction and can each have its own set of engineering and/or performancerequirements. The zones and/or Diameter agent functions can scaledifferently. In one embodiment, one or more of the network elements canspan both the HSS relay zone 110 and the PCC zone 120.

The HSS relay zone 110 can include all network elements or Diameternodes including all functions that communicate with the MobileManagement Entity (MME) and with the HSS, which can be embodied in aCommon Network Repository (CNR) 505. These Diameter nodes can includethe Serving GPRS Support Node (SGSN), the Gateway Mobile Location Center(GMLC), and the Bootstrapping Function (BSF). These Diameter Nodes canalso include the Interrogating/Serving Call Session Control Function(I-/S-CSCF), the Application Server(s) (AS), and the ServiceCentralization & Continuity (SCC) AS, which, for example, may span theHSS relay zone 110 and the PCC zone 120, although the exemplaryembodiments can also include these Diameter nodes in only one zone orthe other.

The PCC zone 120 can include Diameter network elements for implementing,enforcing and controlling charging and policy. For example, in oneembodiment, the Diameter network elements and/or the implementedfunctions can be those that are part of the 3GPP Policy and ChargingControl architecture defined in 3GPP TS 23.203 and the ChargingArchitecture defined in 3GPP TS 32.240, the disclosures of which arehereby incorporated by reference. The PCC zone 120 can support bothinternal and external Online Charging Systems (OCSs) and can include anOnline Business Logic Function (OBLF) to mediate IMS level onlinecharging. Network 500 can utilize real-time session management and QoS,which involve the synchronization and simultaneous use of charging andpolicy control, to intertwine these functions and their correspondingnetwork elements.

The PCC zone 120 can include the Policy Control Resource Function(PCRF), the Policy Control Enforcement Point (PCEF), the ApplicationFunction (AF) which can be the Proxy CSCF (P-CSCF), the SubscriberProfile Repository (SPR) which can be embodied in the CNR, the OnlineCharging System (OCS), the Offline Charging System (OFCS) which can beimplemented by a Charging Data Function (CDF) and Charging GatewayFunction (CGF), the AS, the Media Resource Controller Function (MRFC),the Traffic Detection Function (TDF), and the Gateway Function (GWF)from the S-CSCF.

The Diameter edge zone 130 can act as an external gateway between theservice provider and other 3^(rd) party networks.

The HSS Relay Zone 110 can utilize a relay agent function such as HSSrelay agent 510. In one embodiment, the HSS relay agent 510 canimplement a Subscriber Location Function (SLF) by relaying Diametermessages to the HSS. As a relay agent, HSS relay agent 510 can modifyrouting information but it does not examine or alter non-routing AVPs.HSS relay agent 510 can maintain transaction state but does not maintainsession state. The HSS relay agent 510 can route all messages to andfrom the HSS, and can route messages between the MME and GMLC via theSLg reference point.

The PCC zone 120 can utilize a proxy and translation agent function suchas PCC proxy agent 520. In one embodiment, the PCC proxy agent 520 canimplement at least the 3GPP DRA proxy agent function described in 3GPP29.213, the disclosure of which is hereby incorporated by reference, forthe policy control network and a combined proxy/translation agent andonline charging business function for the charging network. The PCCproxy agent 520 can map policy control network elements (e.g., PCRF,SPR, OCS) and/or charging network elements (e.g., OCS, AS) together on aper user and/or per session basis. In one embodiment, the PCC proxyagent 520 can create a binding per user session between the PCRF andvarious network elements and also between the OCS and various networkelements. In one embodiment, for certain use cases involving onlinecharging, the PCC proxy agent 520 can execute business logic resultingin the modification of Diameter charging messages. As a proxy agent, thePCC proxy agent 520 is able to modify Diameter messages and as atranslation agent, it is able to interwork between Diameter applicationsand between Diameter and other AAA protocols (e.g., RADIUS messages).The PCC proxy agent 520 can maintain both transaction and session state.The PCC proxy agent 520 can route all messages to and from the PCRF andto and from the OCS. In one embodiment, the routing of offline chargingmessages can be static and does not go through the PCC proxy agent 520.In another embodiment, the PCC proxy agent 520 can perform thetranslation agent function between 3^(rd) party external network OCS(e.g., via DEA 530 described later) and the network elements.

The Diameter edge zone 130 can use a proxy agent function such as aDiameter Edge Agent (DEA) 530. In one embodiment, the DEA 530 can be aproxy agent that implements at least the edge agent function describedin GSMA PRD IR.88, the disclosure of which is hereby incorporated byreference. The DEA 530 can provide an “outer” proxy function for variousexternal network connectivity, which may or may not be connectivity withan external network(s) operated by a 3^(rd) party. As a proxy agent, DEA530 can be capable of modifying Diameter messages. DEA 530 can maintainboth transaction and session state. In one embodiment, the DEA 530 canperform various security functions including one or more of topologyhiding, IPSec, and screening.

The HSS relay zone 110 can make use of a session stateless diameteragent function and therefore can be described as “stateless” while thePCC and DEA Zones 120, 130 can make use of session stateful agents. ThePCC and DEA Zones 120, 130 may be described as “stateful.” In oneembodiment, the PCC proxy agent and the DEA are proxy and translationagents.

Referring to FIG. 6, tables 600 describe an exemplary configuration ofinterfaces that can be utilized by the network elements and Diameteragents of network 500. In this example, standardized Diameter interfacesand applications can be implemented by the network 500, althoughproprietary or other interfaces and/or extensions can also be utilizedin combination with, or in place of, one or more of the standardizedinterfaces and/or applications.

The OBLF in the PCC zone 120 may be integrated into the PCC proxy agent520 or it may be implemented as a stand-alone function device. In oneembodiment, the OCS shown within the PCC zone 120 may evolve into acomplete OCS as defined in 3GPP 23.240, the disclosure of which ishereby incorporated by reference, including providing support for anOnline Charging Function (OCF), an Account Balance Management Function(ABMF), and a Rating Function (RF), which may also be located in the PCCzone 120, including resident on the OCS server or on another device(s).In another embodiment, the OCS may support real-time session managementat both the bearer level (e.g., via Sy and Gy/Ro interfaces) and/or atthe IMS level (e.g., via the Ro interfaces). In one embodiment, thenetwork 500 can support 3^(rd) Party OCS(s), which are connected to thePCC zone 120 via the DEA 530. In another embodiment, one or moreadditional Diameter agents may be implemented for the Gz/Rf and Rfinterfaces.

Referring to FIGS. 7 and 8, the network 500 can implement real-timesession management via a continuous, two-step process 700 that includesauthorization of resources followed by a report describing the usage ofthose resources, as shown in FIG. 7. In one embodiment of network 500,authorization for an Enhanced Packet Core (EPC) can be enabled throughthe use of policy control and reporting, which utilizes credit controlmechanisms (i.e., charging). In another embodiment of network 500,authorization for the IMS can be implemented by using policy controland/or by logic residing within an AS. In this example, similar to theEPC, reporting can be implemented using credit control. FIG. 8illustrates a process 800 that enables policy control and charging to beintertwined in the network 500. Process 800 is a superposition of tworeal-time session management processes: one operating at the bearerlevel (i.e., the EPC) and one at the service layer (e.g., the IMS).

The real-time session management of network 500 in the EPC can involvethe use of charging and policy control via the Gy, Sy, and Gx referencepoints as depicted by the arrows 810, 820 in FIG. 8. Real-time chargingreports can be provided by the PCEF to the OCS via the Gy referencepoint. The OCS, in turn, can provide information about charging relatedevents to the PCRF via the Sy interface in a spending limit report. Asan example, the spending limit report can be provided according to 3GPPTS 29.219, the disclosure of which is incorporated by reference,although other procedures or guidelines can be utilized for providingthe report. The PCRF can then provide updated PCC rules to the PCEF viathe Gx reference point, and the PCEF may provide event information backto the PCRF.

The real-time session management of network 500 in the IMS can involvethe use of charging and may involve the use of policy control via theRx, Sd, and Gx reference points as shown by the arrows 820, 830 in FIG.8. Real-time charging reports can be provided by the AS to the OCS viathe Ro reference point. The OCS, in turn, may authorize the use ofadditional resources. Policy control may be modified by the AF on behalfof an AS. In one embodiment, SIP can be utilized as a method ofcommunication between the AS and the AF (represented by a dashed line).

The use of policy control and charging can be intertwined for real-timeservices because in this embodiment charging is used as the reportingmechanism while policy control is used as an authorization mechanism,and both share a common functions, which are the OCS, PCRF, and PCEF.

To achieve the target architecture of network 100 and/or 500, multipleimplementations can evolve as shown in FIGS. 9-11. In one embodiment,this evolution can include the deployment of Diameter interfaces, thedeployment and consolidation of Diameter agents, and the replacement ofproprietary interfaces with standardized interfaces. FIG. 9 illustratesthe evolution process 900 in which some or all of existing Diameterarchitecture silos can be integrated and some or all of vendorproprietary protocols can be replaced with standards-based and/orservice provider-based proprietary protocols. FIG. 10 illustrates amapping 1000 of a “de facto” baseline architecture 1010 created based onrealignment and integration of separate networks operating underDiameter protocol which can be further realigned and/or modified tocreate the target architecture, such as network 100 or 500. Forinstance, the HSS, that is part of the IMS, can be combined with the EPCnetwork to create the HSS relay zone 110. The policy control network,the OCS network and the offline charging can be combined to create thePCC zone 120. The Diameter edge functions can be combined into a singleDiameter edge zone. One or more of the proprietary applications can bereplaced with standardized applications. In one embodiment, the Prop 1interface to the 3^(rd) party external network is not replaced.

FIG. 11 illustrates the transformation or evolution of multiple silo'edcommunication system infrastructures into the de facto baselinearchitecture 1105 which then can further evolve into the targetarchitecture of network 100 or 500. The baseline architecture 1105 priorto evolution to the target architecture of network 500 includesfunctions and/or devices, some or all of which can be retained for usein the network 500 with or without modification. One or more of theexemplary embodiments can also eliminate in whole or in part one or moreof the functions and/or devices described with respect to the baselinearchitecture 1105 when implementing network 100 or 500.

The infrastructure of the baseline architecture 1105 can include EPCnetwork 1150, the IMS network 1160, the Charging network 1170 and thePolicy Control network 1180. The baseline EPC network 1150 can utilizetwo Diameter agents, where one agent is stateless and routes messages toand from the HSS within the EPC. In addition to HSS routing, this agentof baseline EPC network 1150 can route location messages between the MMEand GMLC (e.g., via the SLg interface). The baseline EPC network 1150can also utilize a separate second agent in EPC network 1150 that issession and transaction stateful and which can be used as a bordergateway to route messages between the EPC and external networks tosupport roaming. The EPC network 1150 can include network elements suchas the HSS which provides the HSS function for the EPS; the MME whichcan be a control plane node within the EPC; the SGSN which can be a 2/3Gpacket core node; and the GMLC which supports location services. TheSGSN of the target architecture of network 500 can be upgraded tosupport roaming from Long Term Evolution (LTE) to 2/3G.

The baseline IMS network 1160 can utilize Diameter protocol for routingmessages to and from the HSS and to transport offline charging messagesto the CDF/CGF. The baseline IMS network 1160 can also make use of astateless Diameter agent to route messages to and from the HSS. Unlikethe baseline EPC network 1150, the baseline IMS network 1160 may notpeer with other networks using a Diameter interface and may operatewithout utilizing a Diameter Edge Agent. Offline charging messages inthe baseline IMS network 1160 can be transported via Diameter protocoldirectly from the network element to the CDF/CGF and Diameter agents maynot route these billing reports because the routing can be staticallydefined between the network elements and the CDF/CGF. In the baselineIMS network 1160, the HSS IMS can provide the HSS function within theIMS and can be separate from the HSS within the EPS while the I- andS-CSCFs can be control plane nodes within the IMS and an Access TransferControl Function (ATCF) and SCC AS can be involved with domain transferfrom the IMS to circuit switched networks. The AS of the baseline IMSnetwork 1160 can provide services to users while the CDF/CGF is theoffline billing function. The baseline OCS network 1170 can include aDiameter Agent/OBLF (DA 5) function to route, translate, and in somecases modify messages between an external OCS and various networkelements including the AS(s), the Generic Billing Gateway (GBG) whichcan be used for SMS billing, the PCRF, and the SPR which can be aLightweight Directory Application Protocol (LDAP)-based database. DA 5of baseline OCS network 1170 can function as a proxy/translation agent,a border gateway, and it can execute operator defined business logicrelated to online charging. DA 5 can route Ro from the AS(s) to theexternal network OCS; translate and route proprietary protocol andproprietary Diameter applications such as Prop 3 to a 3^(rd) partyproprietary Diameter application labeled Prop 1; and communicate with anSPR database via Prop 5 which can be LDAP-based or Diameter-based andcan use this information to execute operator defined business logicrelated to online charging.

The baseline PCC network 1180 can utilize three stateful Diameter proxyagents. One proxy agent, called DA 3, can route messages to and from thePCRF within the PCC network 1180 and can map policy control networkelements together on a user session basis while supporting standard andseveral proprietary Diameter applications such as Prop 4 and Prop 6, aswell as LDAP-based Prop 5. The baseline PCC network 1180 can utilizeanother separate proxy agent, called DA 4, and can route messagesbetween the PCRF and an OCS as well as HTTP provisioning flows from aBusiness Support System (BSS) and the OCS, while supporting theproprietary Diameter application Prop 6. The baseline PCC network 1180can utilize yet another Diameter agent as a border gateway to routemessages between the PCC network 1180 and external networks to supportroaming. The baseline PCC network 1180 can have six network elementsthat include the PCRF which determines the policy rules; the PCEF whichis responsible for enforcing the policies determined by the PCRF; theP-CSCF which is an IMS control plane network element that functions inthe PCC network 1180 as an AF; and an OCS that provides balancemanagement capabilities and is provisioned by the BSS. The SPR ofbaseline PCC network 1180 can contain subscription information. Baselinearchitecture 1105 illustrates the integration, in whole or in part, offour separate Diameter networks, three of which utilize an “outer proxy”to connect to external Diameter networks.

In one embodiment, the baseline architecture 1105 of FIG. 11 can bemodified by the SCC AS being connected to DA 1 Diameter via an Shinterface and placed within the EPC network 1150, and the P-CSCF beingconnected to the CDF/CGF via an Rf interface.

In the baseline architecture 1105, the AS can span both the IMS and OCSnetworks while the PCRF can span both the PCC and OCS networks. The HSSwithin the EPS and IMS can remain separate and can be located withintheir respective Diameter networks. “Inner proxies” can route Diametermessages within a Diameter network while “outer proxies” can routemessages to and from an external Diameter network. The baselinearchitecture 1105 can make use of proprietary Diameter applications, aswell as standardized Diameter applications. In integrating the baselinearchitecture 1105, there can be seven different Diameter agents in use.Two of these Diameter agents can be located in the EPC network 1150,three in the PCC network 1180, one in the HSS network 1160, and one inthe OCS network 1170. Referring to FIG. 12, table 1200 provides anexemplary summary of the Diameter agents and the applications that canbe utilized by the baseline architecture 1105.

The baseline architecture 1105 can evolve into the target architecture500 which reduces redundancy of the Diameter agents and more efficientlyroutes and processes the Diameter messages. For example, the PCC proxyagent 520 can take over the functions of or otherwise replace DA 3, DA 4and DA 5 of the baseline architecture 1105. As another example, the HSSrelay agent 510 can take over the functions of or otherwise replace DA 1and DA 2 of the baseline architecture 1105.

Referring to FIGS. 13-16, an exemplary process for transitioning the defacto architecture 1105 into the three zone target architecture ofnetwork 500 is depicted through a multi-stage evolution. The transitionprocess involves deploying Diameter interfaces, deploying andconsolidating agents, and replacing proprietary applications withstandard ones. In this example, there are four stages 1300, 1400, 1500and the final stage which is network 500. In one embodiment, stage 1300can be implemented at the same time as deployment of an LTE network. Inthe HSS Relay Zone 110, the HSS and MMEs can be deployed and directlyconnected to each other via an S6a interface. In the PCC Zone 120, thePCRF, PCEF, SPR (which in this case is an LDAP-based database), and anOCS can be deployed and can communicate with each other via proprietaryDiameter and LDAP applications, such as Prop 4, Prop 5, and Prop 6. Prop4 is a proprietary Diameter application from a vendor and is based on3GPP Gx with additional AVPs to support charging. Prop 5 is aproprietary LDAP application that can communicate between the PCRF andthe SPR. Another proprietary Diameter application, Prop 6, can beintroduced between the PCRF and an OCS to support session based pricingand it can transport policy control information, quota, and usagereports.

In stage 1400, the SGSN, GMLC, and associated interfaces can be deployedand added to the HSS Relay Zone 110. These new interfaces can includeS6d, SLg, and SLh. An HSS Relay function, called DA 1, can be deployedand used to route messages within the HSS Relay Zone 110. Roaming can besupported by the deployment of a DEA 530 which serves as an “outer”proxy for the S6a interface. In the PCC Zone 120, new Diameterapplications can be introduced and the PCC Proxy function can berealized by the deployment of three Diameter agents: DA 3 can implementthe 3GPP DRA function and can route proprietary Diameter and LDAPmessages between the PCRF, PCEF, and the SPR; DA 4 can route proprietaryDiameter messages between the OCS and the PCRF as well as HTTPprovisioning flows between a BSS and the OCS; and DA 5 can route andinterwork proprietary Diameter messages between the PCRF and theexternal network OCS (which can be a 3^(rd) party network) and canimplement the OBLF. An enhanced version of Prop 6, labeled Prop 3, canbe deployed between the PCRF and DA 5. DA 5 can interwork thisapplication with a proprietary application of the external network, suchas Prop 1 which lies between the OBLF and the external network OCS.

In one embodiment, stage 1500 can coincide with the deployment of IMS.In the HSS relay zone 110, the HSS, AS, and SCC AS can be deployed andcan communicate with each other via the Cx and Sh interfaces through anHSS Relay function called DA 2. Together, DA 1 and DA 2 can realize orotherwise provide the HSS Relay function. In the PCC zone 120, the IMSlevel offline and online charging can be implemented along with the S9interface for roaming. Offline charging for the packet core and severalnewly deployed IMS nodes, including the AS, SCC AS, I-/S-CSCF, ATCF,MRFC, and Media Gateway Control Function (MGCF) can be supported via theGz/Rf and Rf interfaces to the CDF/GCF, respectively. A Diameter agentfunction may not be required between some of these network elementsbecause the routing can be expected to be substantially static and thedelivery of the messages is deemed not time sensitive. Online chargingfor the As(s) can be supported via the Ro interface to the externalnetwork OCS via DA 5 which may act as a proxy agent and a DEA. A Prop 5application can be introduced between DA 5 and the SPR to support theOCS Business Logic Function. The S9 interface can be deployed to supportroaming scenarios that involve policy control. DA 3 can be used to routethe messages associated with the S9 interface to the DEA which providesthe “outer” proxy role.

The final stage of the evolution results in network 500 illustrated inFIG. 5. Network 500 can be created from stage 1500 by the addition ofnew Diameter nodes and interfaces, Diameter agent consolidation, and thereplacement of proprietary interfaces. Three new Diameter nodes can beintroduced: the AF that is separate from the P-CSCF; the TDF, and theBSF. The new instance of AF can connect to the PCRF via the Rx interfaceand may be used for services that do not involve IMS. The TDF connectsto the PCRF via the Sd interface. The BSF can connect to the CNR via theZh interface. Both the Rx and the new Sd interface can be routed via thePCC proxy function 520 while the new Zh interface can be routed by theHSS relay function 510.

Referring to FIG. 17, a method of creating a target architecture, suchas network 500, is illustrated. It should be understood that theparticular order of the method steps can be rearranged and that themethod can be operated with more or less steps than is illustrated.Further, one or more of these steps can be combined or can beeliminated. In step 1702, DA 1 and DA 2 may be consolidated into asingle HSS proxy platform that supports both the EPC and the IMS, viaconsolidating the HSS, and SPR into the CNR. This can be accomplished byupgrading, if necessary, DA 1 and DA 2 to a common software platformthat supports both EPC and IMS reference points and then interconnectingDA 1 and DA 2 to both EPC and IMS network elements. In step 1704, DA 3,DA 4, and DA 5 may be consolidated into a single PCC proxy platform intwo steps. The first step is to consolidate DA 3 and DA 4 into a singleplatform. This may be accomplished in several ways including upgradingboth platforms to support both roles or upgrading one platform tosupport both roles and the retiring of the other. In the second step, DA5 can be consolidated with the newly created DA 3/DA 4 platform tocreate a single PCC proxy platform. Like the DA 3/DA 4 consolidation,this may be done in several ways including upgrading DA 5 and DA 3/DA 4to a common set of functions and using both or upgrading one of the twoand retiring the other. The OBLF may be integrated into the new PCCproxy platform or implemented as a separate entity. In addition, innetwork 500, DA 5 may no longer be used as an “outer” proxy to theexternal network or other 3^(rd) party OCS as this function can beprovided by the DEA 530. In one embodiment, if an internal OCS can beintroduced for IMS charging, the Ro reference point can connect to itvia the PCC proxy agent 520. In step 1706, the Diameter edge functionsfrom the separate Diameter networks can be combined into a singleDiameter edge zone.

In one embodiment in step 1708, the transition to network 500 caninclude some or all of the vendor proprietary applications (e.g., withinthe PCC zone 120) being replaced with standard applications (e.g., 3GPP)that may contain service provider extensions. Prop 4, Prop 6, and Prop 3may be replaced with Gx, Gy, and Sy. Prop 5 may be replaced with the3GPP specified Sp reference point or the LDAP-based Ud reference point.The Prop 1 interface between the external network OCS and the OBLF canremain in place. In one embodiment, network 500 can support theinterrogation of out-of region HSSs. In another embodiment, network 500can include both internal and external OCSs. For instance, the internalOCS can support both bearer and IMS level charging. The internal OCS(s)may also support Sy, Gy/Ro, and Ro interfaces. In one embodiment, the Spreference point may be Diameter based or may be based on anotherprotocol, such as based on LDAP. In one embodiment, the Gy/Ro referencepoint is supported on the PCEF.

Referring to FIG. 18, a method of supporting subscriber management forEPS and IMS networks, such as network 500, is illustrated. It should beunderstood that the particular order of the method steps can berearranged and that the method can be operated with more or less stepsthan is illustrated. Further, one or more of these steps can be combinedor can be eliminated. In step 1802, HSS relay agent 510 can be utilizedfor a communication session based on one or both of the EPS and IMScomponents of network 500. The HSS relay agent 510 can receive messagesassociated with the communication session, which can be one or more ofvoice, video and data sessions. In step 1804, the HSS relay agent 510can maintain transaction state associated with the communication sessionwithout maintaining session state. For example, the HSS relay agent 510can ignore or otherwise not expend processing resources for non-routinginformation (e.g., non-routing AVPs) in the messages while selectivelyadjusting routing information (e.g., routing AVP's). In the exemplaryembodiment of network 500, the messages received by and transmitted fromthe HSS relay agent 510 are according to Diameter protocol. However, theexemplary embodiments can operate according to other protocols incombination with, or in place, of the Diameter protocol, such as RADIUSprotocol. In one embodiment of method 500, all messages that aretransmitted to and from the HSS relay agent 510 are according to thesame protocol (e.g., Diameter protocol). In another embodiment, allmessages being routed within the HSS relay zone 110, the PCC zone 120and the Diameter Edge zone 130 are according to the same protocol, suchas a Diameter protocol.

In step 1806, the HSS relay agent 510 can support a subscriber locationfunction by determining an appropriate HSS (which can be embodied in theCNR of network 500) and/or routing message(s) to the HSS. In oneembodiment, this can enable the exchange of subscription-relatedinformation (e.g., subscriber profiles), performance of authenticationand authorization of the user(s), and/or providing information about thesubscriber's location and IP information.

In step 1808, the HSS relay agent 510 can be utilized for routingmessage(s) between a mobile Management entity and a gateway mobilelocation center. In one embodiment, this can enable idle mode UE (UserEquipment) tracking and paging procedure including retransmissions;bearer activation/deactivation processing; selection of a SGW for a UEat the initial attach and at time of intra-LTE handover involving CoreNetwork (CN) node relocation; authenticating the user via interactingwith the HSS; generation and allocation of temporary identities to Ue's;checking the authorization of the UE to camp on the service provider'sPublic Land Mobile Network and enforcing UE roaming restrictions; beingthe termination point in the network for ciphering/integrity protectionfor NAS signaling and handling the security key management; lawfulinterception of signaling; and/or providing the control plane functionfor mobility between LTE and 2G/3G access networks. In anotherembodiment, this can enable supporting LoCation Services (LCS);requesting routing information from the HSS; sending positioningrequests to the Visited Mobile Switching Centre (VMSC) or SGSN SupportNode) or MSC (Mobile Switching Centre) Server; and/or receiving finallocation estimates from the corresponding entity.

In step 1810, the HSS relay agent 510 can be utilized for routingmessages to and from the bootstrapping function. In one embodiment, thiscan enable application independent functions for mutual authenticationof user equipment and servers unknown to each other; ‘bootstrapping’ theexchange of secret session keys afterwards; utilization of services thatneed authentication and secured communication such as Mobile TV and PM;routing for the Generic Authentication Architecture (GAA); arrangingsecurity relation between the UE and Network Application Function (NAF);and/or building a security relation with a previously unknown devicefirst and allowing installing security elements (keys) in the device andthe BSF afterwards. In another embodiment, this can enable the BSF to beintroduced by the NAF, after an unknown UE device is trying to getservice access; the NAF referring the UE to the BSF; the UE and BSFmutually authenticating via 3GPP protocol AKA (Authentication and KeyAgreement); the BSF sending related queries to the HSS; the UE and BSFagreeing on a session key to be used for encrypted data exchange withthe NAF; the UE again connecting to the NAF; the NAF being able toobtain the session key as well as user specific data from the BSF;and/or data exchange commencing with the UE using the related sessionkeys for encryption.

Referring to FIG. 19, a method of supporting policy control and chargingfor EPS and IMS networks, such as network 500, is illustrated. It shouldbe understood that the particular order of the method steps can berearranged and that the method can be operated with more or less stepsthan is illustrated. Further, one or more of these steps can be combinedor can be eliminated. In step 1902, PCC proxy agent 520 can be utilizedfor a communication session based on one or both of the EPS and IMScomponents of network 500. The PCC proxy agent 520 can identify thecommunication session and receive messages associated with thecommunication session, which can be one or more of voice, video and datasessions. In step 1904, the PCC proxy agent 520 can maintain transactionstate and session state associated with the communication session. Forexample, the PCC proxy agent 520 can selectively adjust non-routinginformation (e.g., non-routing AVPs) in the messages and/or selectivelyadjust routing information (e.g., routing AVP's). In the exemplaryembodiment of network 500, the messages received by and transmitted fromthe PCC proxy agent 520 are according to Diameter protocol. However, theexemplary embodiments can operate according to other protocols incombination with, or in place, of the Diameter protocol, such as RADIUSprotocol. In one embodiment of method 500, all messages that aretransmitted to and from the PCC proxy agent 520 are according to thesame protocol (e.g., Diameter protocol). In another embodiment, allmessages being routed within the HSS relay zone 110, the PCC zone 120and the Diameter Edge zone 130 are according to the same protocol, suchas a Diameter protocol.

In step 1906, the PCC proxy agent 520 can support a policy control forthe communication session by routing messages associated with the policycontrol to policy control network elements, such as the Policy ControlResource Function, the Subscriber Profile Repository, and/or the OnlineCharging System. In step 1908, the PCC proxy agent 520 can supportcharging for the communication session by routing messages associatedwith the charging to charging network elements, such as the ApplicationServer(s) and/or the Online Charging System. The exemplary embodimentscan include combining steps 1906 and 1908. The PCC proxy agent 520 canperform mapping among the policy control network elements and/or thecharging network elements. In one embodiment, this mapping can beperformed on a per user and/or per session basis. In one embodiment,this can enable real-time session management that intertwines policycontrol and all levels of charging (e.g., bearer, IMS, services) throughuse of a continuous, two-step process that includes authorization ofresources followed by a report describing the usage of those resources.In one embodiment, to simplify the operation of the network, a PCC proxyagent 520 that supports both policy control and all levels of chargingcan be utilized.

In step 1910, the PCC proxy agent 520 can be utilized for executingbusiness logic function including operator defined logic, which may beperformed directly by the server upon which the PCC proxy agent 520 isresident and/or may be executed by a separate OBLF server as shown inFIG. 5. In step 1912, the PCC proxy agent 520 can be utilized fortranslation between different protocols, such as via a translation agentof the server upon which the PCC proxy agent is resident. For example,the PCC proxy agent 520 can translated between Diameter protocol andother protocols, including other AAA protocols such as RADIUS.

The network elements of HSS relay zone 110 and PCC zone 120 can functionto provide communication sessions for users, including voice, videoand/or data communications. In one embodiment, the network elements canfunction similarly to LTE and/or IMS systems, but with the messagerouting being under the control of the Diameter agents described hereinfor each of the zones.

In one embodiment, combined services for circuit-switched andpacket-switched communications can be facilitated by network 500including for IMS-compliant communication devices and Public SwitchedTelephone Network communication devices. For example, network 500 canutilize the P-CSCF, I-/S-CSCF and CNR for registration. Communicationsession initiation and subscriber service implementation can be providedvia SIP INVITE message utilizing P-CSCF, S-CSCF and AS. In someinstances the aforementioned communication process is symmetrical. It isfurther noted that the communications of network 500 can be adapted tosupport video conferencing and the end user devices can operate aswireline and/or wireless devices. In one embodiment, the communicationdevice can be communicatively coupled to a cellular base station, afemtocell, a WiFi router, a DECT base unit, or another suitable wirelessaccess unit to establish communications with network 500.

In one embodiment, network 500 can support communications associatedwith wireless access protocols such as Global System for Mobile (GSM),Code Division Multiple Access (CDMA), Time Division Multiple Access(TDMA), Universal Mobile Telecommunications (UMTS), Worldinteroperability for Microwave (WiMAX), Software Defined Radio (SDR),Long Term Evolution, and so on. Other present and next generationwireless network technologies can also be supported by the exemplaryembodiments described herein.

The network 500 can represent a single instance of zones of networkelements or there can be many instances of the zones of network elementsshown in FIG. 5. In one embodiment, all messages that are communicatedwithin zones 110, 120, 130 of the network 500 are done so utilizingDiameter protocol. In another embodiment, the HSS relay agent 510 doesnot examine or otherwise process any non-routing information (e.g.,non-routing AVPs) of a message while the PCC proxy agent 520 and the DEAcan selectively examine (or otherwise process) and/or adjust some or allmessages, including routing and non-routing AVP's.

The exemplary embodiments describe utilizing proxy, relay and/ortranslation agents for routing messages within the various zones ofnetwork 500. These examples are described with respect to operationutilizing the Diameter protocol. However, one or more embodiments canutilize other protocols in combination with or in place or the Diameterprotocol, including utilizing a combination of the Diameter protocol andRADIUS protocol (or another protocol) for messages being provided withinthe network 500. The exemplary embodiments can also interchange which ofthe agents are utilized in which of the zones so that one or more of therelay, proxy and translation can be utilized in each of the zones indifferent configurations. In one embodiment, one or more of the zonescan utilize a different protocol than one or more other zones, such asthrough use of a translation agent routing messages between the zones.For example, Diameter protocol can be used in the HSS relay zone 110while RADIUS or another protocol can be used for certain interfaces inthe PCC zone 120. One or more of the exemplary embodiments can alsooperate, in whole or in part, in conjunction with other packet-basedsignaling protocols, including Authentication, Authorization andAccounting (AAA) protocols, such as RADIUS protocol.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeuni-directional and/or bi-directional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 20 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 2000 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods discussed above. One or more instances of the machine canoperate, for example, as the Diameter Agents and the network elements ofnetworks 100, 500, and/or 1105 shown in FIGS. 1, 5 and 11 as describedabove. In some embodiments, the machine operates as a standalone device.In some embodiments, the machine may be connected (e.g., using anetwork) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine inserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet PC, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the present disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 2000 may include a processor 2002 (e.g., a centralprocessing unit (CPU), a graphics processing unit (GPU, or both), a mainmemory 2004 and a static memory 2006, which communicate with each othervia a bus 2008. The computer system 2000 may further include a videodisplay unit 2010 (e.g., a liquid crystal display (LCD), a flat panel,or a solid state display. The computer system 2000 may include an inputdevice 2012 (e.g., a keyboard), a cursor control device 2014 (e.g., amouse), a disk drive unit 2016, a signal generation device 2018 (e.g., aspeaker or remote control) and a network interface device 2020.

The disk drive unit 2016 may include a non-transitory machine-readablemedium 2022 on which is stored one or more sets of instructions (e.g.,software 2024) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above. Theinstructions 2024 may also reside, completely or at least partially,within the main memory 2004, the static memory 2006, and/or within theprocessor 2002 during execution thereof by the computer system 2000. Themain memory 2004 and the processor 2002 also may constitutemachine-readable media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Applications that may include the apparatusand systems of various embodiments broadly include a variety ofelectronic and computer systems. Some embodiments implement functions intwo or more specific interconnected hardware modules or devices withrelated control and data signals communicated between and through themodules, or as portions of an application-specific integrated circuit.Thus, the example system is applicable to software, firmware, andhardware implementations.

In accordance with various embodiments of the present disclosure, themethods described herein are intended for operation as software programsrunning on a computer processor. Furthermore, software implementationscan include, but not limited to, distributed processing orcomponent/object distributed processing, parallel processing, or virtualmachine processing can also be constructed to implement the methodsdescribed herein.

The present disclosure contemplates a machine readable medium containinginstructions 2024, or that which receives and executes instructions 2024from a propagated signal so that a device connected to a networkenvironment 2026 can send or receive voice, video or data, and tocommunicate over a network 2026 using the instructions 2024. Theinstructions 2024 may further be transmitted or received over thenetwork 2026 via the network interface device 2020.

While the machine-readable medium 2022 is shown in an example embodimentto be a single medium, the term “machine-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of themethods of the present disclosure.

The term “machine-readable medium” shall accordingly be taken toinclude, but not be limited to: solid-state memories such as a memorycard or other package that houses one or more read-only (non-volatile)memories, random access memories, or other re-writable (volatile)memories; and magneto-optical or optical medium such as a disk or tape.Accordingly, the disclosure is considered to include any one or more ofa machine-readable medium or a distribution medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having similarfunctions or essentially the same functions. Wireless standards fordevice detection (e.g., RFID), short-range communications (e.g.,Bluetooth, WiFi, Zigbee), and long-range communications (e.g., WiMAX,GSM, CDMA) are contemplated for use by computer system 2000.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Otherembodiments may be utilized and derived therefrom, such that structuraland logical substitutions and changes may be made without departing fromthe scope of this disclosure. Figures are also merely representationaland may not be drawn to scale. Certain proportions thereof may beexaggerated, while others may be minimized. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement calculated toachieve the same purpose may be substituted for the specific embodimentsshown. This disclosure is intended to cover any and all adaptations orvariations of various embodiments. Combinations of the aboveembodiments, and other embodiments not specifically described herein,will be apparent to those of skill in the art upon reviewing the abovedescription. The exemplary embodiments can include utilizing acombination of one or more features of different embodiments, includingcombining devices and/or method steps from two or more differentembodiments.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. An apparatus comprising: a memory storingexecutable instructions; and a processing system including a processorcoupled with the memory, wherein the processing system, responsive toexecuting the instructions, facilitates performance of operationscomprising: receiving, via network connections at the apparatus,messages based on an Evolved Packet System network and an InternetProtocol Multimedia Subsystem network, wherein the messages utilize aDiameter protocol from first network elements that provide policycontrol and charging for a communication session based on the EvolvedPacket System network and the Internet Protocol Multimedia Subsystemnetwork, wherein the first network elements include a Policy ControlResource Function server, a Policy Control Enforcement Point server, aProxy Call Session Control Function server, a Subscriber ProfileRepository, and an Online Charging System that communicate with eachother only via the apparatus, wherein the apparatus is a separate devicefrom the Policy Control Resource Function server, the Policy ControlEnforcement Point server, the Proxy Call Session Control Functionserver, the Subscriber Profile Repository, and the Online ChargingSystem, and wherein all messages based on the Evolved Packet Systemnetwork and the Internet Protocol Multimedia Subsystem network, to andfrom the Policy Control Resource Function server and the Online ChargingSystem, are routed through the apparatus, wherein the apparatus is asingle server, and wherein the Policy Control Resource Function server,the Policy Control Enforcement Point server, the Proxy Call SessionControl Function server, the Subscriber Profile Repository, and theOnline Charging System communicate directly with the apparatus via thenetwork connections; maintaining, at the apparatus, transaction andsession state during the communication session, wherein the processingsystem selectively adjusts routing attribute value pairs and non-routingattribute value pairs for the messages; routing, from the apparatus, themessages utilizing the Diameter protocol to second network elements thatprovide the policy control and charging; and providing, from theapparatus, at least one of the messages to a Diameter edge agentfunction that maintains transaction and session state during thecommunication session for routing the at least one of the messages to anexternal network.
 2. The apparatus of claim 1, wherein a first portionof the messages authorize resource usage, and wherein a second portionof the messages are responsive to the first portion of the messages andreport the resource usage.
 3. The apparatus of claim 2, wherein thefirst portion of the messages includes a spending limit usage reporttransmitted from an offline charging system to the Policy ControlResource Function server via the apparatus.
 4. The apparatus of claim 3,wherein the operations further comprise mapping at least a portion ofthe first and second network elements to each other on a per user and aper session basis, and wherein the network connections comprise one ofSy interface, Gy/Ro interface, Gx interface, Rx interface, Sp interface,Sd interface, S9 interface, Gz/Rf interface, or any combination thereof.5. The apparatus of claim 1, wherein the first and second networkelements include a Media Resource Controller Function server, a TrafficDetection Function server, and a gateway function.
 6. The apparatus ofclaim 1, wherein the operations further comprise performing an onlinecharging business logic function.
 7. The apparatus of claim 1, whereinthe operations further comprise performing mapping among the PolicyControl Resource Function server, the Subscriber Profile Repository, theOnline Charging System and an application server.
 8. The apparatus ofclaim 1, wherein the operations further comprise selectivelyimplementing a translation agent to translate between the Diameterprotocol and another protocol for the messages.
 9. The apparatus ofclaim 1, wherein all messages routed via the processing system utilizethe Diameter protocol, and wherein the at least one of the messages thatis routed from the processing system to the Diameter edge agent functionis translated from the Diameter protocol to another protocol by theDiameter edge agent function.
 10. The apparatus of claim 1, wherein therouting of the messages facilitates establishing communicationsutilizing the Evolved Packet System network and the Internet ProtocolMultimedia Subsystem network.
 11. The apparatus of claim 1, wherein allmessages transmitted from the processing system to the external networkare routed through the Diameter edge agent function.
 12. A methodcomprising: routing messages that utilize a Diameter protocol, vianetwork connections by a first agent function of a system, betweennetwork elements that provide policy control and charging forcommunication sessions, wherein the network elements include a PolicyControl Resource Function server a Policy Control Enforcement Pointserver, a Proxy Call Session Control Function server, and a SubscriberProfile Repository that communicate with each other only via the firstagent function, wherein the system executing the first agent function isseparate from the Policy Control Resource Function server, PolicyControl Enforcement Point server, the Proxy Call Session ControlFunction server, and the Subscriber Profile Repository, and an OnlineCharging System, wherein the messages are based on an Evolved PacketSystem network and an Internet Protocol Multimedia Subsystem network,wherein the system is a single server, and wherein the Policy ControlResource Function server, the Policy Control Enforcement Point server,the Proxy Call Session Control Function server, the Subscriber ProfileRepository, and the Online Charging System communicate directly with thesystem via the network connections; maintaining, by the first agentfunction, transaction and session state during the communicationsessions, wherein the communication sessions are based the EvolvedPacket System network and the Internet Protocol Multimedia Subsystemnetwork; selectively adjusting, by the first agent function, routinginformation and non-routing information for the messages; and providingat least one of the messages to a Diameter edge agent function thatmaintains transaction and session state during the communicationsessions for routing the at least one of the messages to an externalnetwork.
 13. The method of claim 12, further comprising: performingmapping among the network elements.
 14. The method of claim 12, whereinthe Diameter edge agent function supports the Evolved Packet Systemnetwork and the Internet Protocol Multimedia Subsystem network.
 15. Themethod of claim 12, wherein the network elements include an OnlineCharging System server, and wherein offline charging messages are routedto bypass the first agent function.
 16. The method of claim 12,comprising utilizing the first agent function to perform an onlinecharging business logic function.
 17. The method of claim 12, whereinthe routing information comprises routing attribute value pairs, andwherein the non-routing information comprises non-routing attributevalue pairs.
 18. The method of claim 12, comprising providing at leastone of the messages to a Diameter edge agent function that utilizes atranslation agent for translating between a Diameter protocol andanother protocol before routing the at least one of the messages to anexternal network.
 19. A non-transitory machine-readable storage mediumcomprising executable instruction, which, responsive to being executedby a processing system including a processor, facilitate performance ofoperations comprising: routing messages based on an Evolved PacketSystem network and an Internet Protocol Multimedia Subsystem network,utilizing a Diameter protocol, via network connections between networkelements that provide policy control and charging for a communicationsession based on the Evolved Packet System network and the InternetProtocol Multimedia Subsystem network, wherein the network elementsinclude a Policy Control Resource Function server, a Policy ControlEnforcement Point server, a Proxy Call Session Control Function server,a Subscriber Profile Repository, and an Online Charging System thatcommunicate with each other via the processing system, wherein theprocessing system is a separate device from the Policy Control ResourceFunction server, the Policy Control Enforcement Point server, the ProxyCall Session Control Function server, the Subscriber Profile Repository,and the Online Charging System, wherein all messages to and from thePolicy Control Resource Function server and the Online Charging Systemare routed through the processing system based on a Diameter protocol,wherein the processing system is part of a single server, and whereinthe Policy Control Resource Function server, the Policy ControlEnforcement Point server, the Proxy Call Session Control Functionserver, the Subscriber Profile Repository, and the Online ChargingSystem communicate directly with the processing system via the networkconnections; maintaining transaction and session state during thecommunication session; selectively adjusting routing and non-routinginformation for the messages; and providing at least one of the messagesto a Diameter edge agent function that maintains transaction and sessionstate during the communication session for routing the at least one ofthe messages to an external network, wherein a first portion of themessages authorize resource usage for the communication session, andwherein a second portion of the messages are responsive to the firstportion of the messages and report the resource usage.
 20. Thenon-transitory machine-readable storage medium of claim 19, wherein theoperations further comprise: performing mapping among the networkelements that include the Policy Control Resource Function server, theSubscriber Profile Repository, the Online Charging System and anapplication server.